This creates the underlying component with creation_ctx, whose link() returns inner_scope. But inner_scope is never mounted — its state is permanently None.

This makes function component hooks permanently broken after load.

When a function component is created, FunctionComponent::new() captures ctx.link().clone() into a re_render closure:

  let re_render = {
      let link = ctx.link().clone(); // this is inner_scope
      Rc::new(move || link.send_message(()))
  };

Every hook (use_state, use_reducer, etc.) shares this closure. When a state setter fires, it calls inner_scope.send_message(()), which schedules an UpdateRunner. But UpdateRunner::run() checks inner_scope.state, finds None, and silently returns. The component renders once correctly and then becomes completely unresponsive to all state changes. I've confirmed this — a simple use_state counter wrapped in declare_lazy_component! renders 0 and clicking the increment button does nothing.

I created a minimal reproducing repo https://github.com/Madoshakalaka/yew-lazy-hook-bug

I suppose the same is true for all messages sent to the components own link which do not get drained correctly. Though both pending_messages and state are Rc, downcasting will later later lead to failures due to misatching generics Lazy<C>!= C and LazyMessage<C::Message> != C::Message.